Method and apparatus for electronic collection, translation, grouping, and delivery of wage assignment information

ABSTRACT

A system electronically collects, translates, groups, and delivers wage assignment information from at least one initiator to at least one recipient via an accumulator. An initiator initially receives the wage assignment information. Then, an accumulator collects the wage assignment information from at least one initiator, such as a government agency. The accumulator then translates the wage assignment information into a format compatible with electronic data interchange (EDI), such as the ANSI X12 standard. The accumulator then groups the EDI wage assignment information into specific files, batching the files based upon one data field contained within the wage assignment information data set, such as a recipient. The accumulator then delivers a batched EDI wage assignment file to each respective recipient. Once the EDI wage assignment file is received by the recipient, the wage assignment may then be implemented.

I. RELATED APPLICATIONS

This application is a continuation of and claims benefit of applicationSer. No. 12/320,702, filed on Feb. 2, 2009, now U.S. Pat. No. 7,877,423which is a divisional of and claims benefit of application Ser. No.11/438,443, filed on May 23, 2006, (now U.S. Pat. No. 7,720,797), whichis a continuation of and claims benefit of application Ser. No.10/155,965, filed on May 29, 2002, (now U.S. Pat. No. 7,072,909), whichis a continuation of and claims the benefit of application Ser. No.09/200,943, filed on Nov. 30, 1998, (now U.S. Pat. No. 6,567,821), whichclaims the benefit of U.S. Provisional Application No. 60/085,731, filedMay 15, 1998, all of which are incorporated herein by reference.

II. BACKGROUND OF THE INVENTION

A. Field of the Invention

The present invention relates generally to the collection, translation,grouping, and delivery of wage assignment information. Moreparticularly, the invention relates to methods and apparatus forelectronic collection of wage assignment information, translation of theinformation into an electronic wage assignment format, grouping of theformatted information into files by batching for each respectiverecipient, and electronic delivery of the batched information files toeach respective recipient.

B. Description of the Related Art

If a private or public entity wishes to collect a financial obligationfrom a particular person, the entity may obtain a judicial orderrequiring that the person make payments to satisfy the obligation.Frequently, the most common method to satisfy a court-ordered orcourt-enforced financial obligation is by requiring that the employerwithhold a portion of the person's salary in the form of a wageassignment. A wage assignment may be implemented either by manual orelectronic means. Manual implementation is the least efficient manner toprocess a wage assignment. Furthermore, even electronic implementationincludes significant temporal and structural inefficiencies, primarilywith regard to the collection, translation, grouping, and delivery ofthe information.

Electronic Implementation of Ware Assignments. Electronic commerce (EC)describes the paperless exchange of business information usingelectronic data interchange (EDI), electronic funds transfer (EFT), andother means of electronic communication. Of these various types ofelectronic communication, EDI allows for the accumulation, processing,transmittal, and receipt of business-related information that was oncedependent on paper transactions. Generally, EDI describes thecomputer-to-computer exchange of business information using a publicstandard. The first such public EDI standard was created by theTransportation Data Coordinating Committee (TDCC), which created thefirst set of industry EDI standards comprising forty-five transactionsets for the transportation industry. These initial EDI transaction setsprovided for the exchange of business information pertaining to ocean,motor, air, and rail carriers and the associated shippers, brokers,customs, freight forwarders, and bankers. Eventually, other businesssegments soon discovered that EDI was a more cost effective means ofcommunicating business transaction information than paper transactions.

For the computer-to-computer exchange of business transactioninformation through EDI, however, a standard format is required forreasons of compatibility. Initially, the TDCC standards controlled, butthese standards were limited to business transactions in thetransportation industry. As the use of EDI expanded, there was a needfor a new, broader standard. In response, the American NationalStandards Institute (ANSI) was tasked with the responsibility ofcreating a new standard, a standard that would include transaction setsfor all types of business information. Yet, while ANSI is thecoordinator and clearing house for national standards in the UnitedStates, ANSI does not write national standards. Instead, ANSI chartersorganizations, called Accredited Standards Committees (ASCs), to prepareconsensus standards. ASCs are composed of voluntary representatives fromindustry, labor, consumer, and government. Periodically, ANSI chartersan ASC to develop a new standard.

One such ASC, the ASC X12, was chartered by ANSI to develop standardsfor the structure, format, and content of electronic businesstransactions conducted through EDI. The ASC X12 is administered by theData Interchange Standards Associations, Inc. (DISA), a not-for-profitcorporation. Under the management of DISA, the ASC X12 composed andissued the ANSI X12 standard (i.e., the X12 standard). Pursuant to theX12 standard, each EDI transaction involves the electronic transmissionof a business document using a particular transaction set. Thus, thetransaction sets (or record sets) in the X12 standard define both thefile structure and content format for communicating electronic businesstransactions using EDI.

Under the X12 standard, there are a number of particular record sets,each set corresponding to a particular type of business transaction. Asof 1994, the X12 standard included 187 record sets. Notably, the variousrecord sets of the X12 standard are delineated by specific numericcodes. For example, record set 135 pertains to student loanapplications, and record set 813 pertains to electronic tax filing. Forpurposes of wage assignments, however, record set 521 is the most commontype of transaction set, as record set 521 pertains to income or assetoffset. Notably, the record set 521 is still under development.Nonetheless, when finally implemented, the 521 record set will make itpossible to electronically communicate wage assignment information.

Therefore, under the X12 standard, there is an EDI transaction set foroffsets from wages or other income (i.e., the 521 record set) thatallows for offsets to wages or other income by means of an electronicimplementation of a wage assignment. As described in the Draft Standardfor Trial Use, 521 Income or Asset Offset, dated May 15, 1997, herebyincorporated by reference, the record set 521 allows for the input ofboth the wage transfer instruction as well as other pertinentinformation related to a wage assignment transaction. The wage transferinstruction and the other information relating to the wage transfer arereferred to collectively as wage assignment information. With wageassignment information, an employer may be instructed to withholdautomatically a predetermined portion of the wage of a particularemployee and to transfer automatically the withheld portion to anotherperson or entity. Thus, for the electronic implementation of a wageassignment, however, the wage assignment information must be collectedfrom an initiating entity; the wage assignment information must then betranslated into the proper electronic format; the wage assignmentinformation must then be batched for each recipient; and the wageassignment information must then be delivered to each respectiverecipient. Furthermore, for this electronic implementation, theinitiator of the wage assignment must be capable of sending the wageassignment information in a proper electronic format, and the recipientmust be capable of receiving the wage assignment information in anelectronic format and then implementing the wage assignment.

However, the present systems and methodologies for the electronicprocessing of wage assignment information are inefficient andundesirable. These shortcomings are demonstrated by the present systemsand methodologies. For purposes of considering the present systems andmethodologies for electronic implementation of wage assignmentinformation, an illustration of one common type of wage assignment isused herein as an example, namely, a wage assignment based on a childsupport obligation. With the present systems and methodologies, pursuantto an order by a judicial entity, a state entity generates a wageassignment order for a noncustodial parent to make child supportpayments to a custodial parent. In almost all cases, the state entitymails the order to the employer of the noncustodial parent. The employerof the noncustodial parent must then process the wage assignmentinformation, so that a withheld wage portion is automatically removedfrom the wage of the noncustodial parent. Notably, for purposes of thepresent systems and methodologies, as set forth below, virtually anytype of wage assignment would be similarly treated as in the example ofa wage assignment based on a child support obligation.

Collection of Wage Assignment Information. For a typical wageassignment, such as, for example, a child support obligation, aparticular state entity is generally responsible for generating the wageassignment orders for every noncustodial parent subject to a wageassignment. In processing the orders, the state entity generally sends awage assignment order to the indicated employer of each noncustodialparent. Thus, large employers generally receive multiple wage assignmentorders. Moreover, in most cases, employers not only receive multiplewage assignment orders from a state entity, but employers also receivemultiple wage assignment orders from multiple state entities. Thiscurrent system is inefficient and undesirable. According to the presentsystems and methodologies, there is no means to collect the wageassignment orders and transmit the orders as a single unit to theemployers, which would allow for the translation of the orders into anEDI format, batching of the files for each recipient, and delivery as asingle EDI transaction. Thus, the present systems and methodologies forcollecting wage assignment information are inadequate.

Translation of Wage Assignment Information. For a typical wageassignment, such as, for example, a child support obligation, the X12standard provides a mechanism for automating the allocation of wageassignment orders for child support payments to employers. Because theX12 standard includes a transaction set for wage assignments (i.e., the521 record set), EDI may be used to process wage assignmentselectronically. However, in most states, wage assignment orders arestill issued on paper. Thus, in these states, wage assignments cannot beimplemented electronically. Further, in the remaining states that mayuse electronic wage assignments, while the wage assignment orders may beelectronically generated, the orders are not issued in a formatcompatible with the X12 standard. Thus, a wage assignment order cannotbe processed as an EDI transaction. As such, the present systems andmethodologies are inefficient and undesirable. Therefore, according tothe present systems and methodologies, there is no means to translateeither the paper or the electronic information produced by the stateagencies into a format compatible with the X12 standard that may then bebatched delivered as an EDI file to employers. Thus, the present systemsand methodologies of translating wage assignment information areinadequate.

Grouping of Wage Assignment Information. For a typical wage assignment,such as, for example, a child support obligation, separate wageassignment orders are issued for each wage assignment. Thus, as notedabove, an employer may not only receive numerous wage assignment ordersbut may also receive numerous wage assignment orders from numerous stateentities. Such inefficiencies strain the resources of employers thatmust adhere to both judicial and governmental requirements regarding theprocessing of wage assignments. The X12 standard provides a means toavoid these inefficiencies by the use of EDI. Using the fields of arecord set from the X12 standard, such as, for example, the 521 recordset, wage assignment orders could be collected, translated and thenbatched for delivery to employers as a single EDI file. However, thepresent systems and methodologies do not provide a means of groupingwage assignment orders by recipient, where the orders are alsocollected, translated, and delivered in a wage assignment collection anddelivery system. Thus, the present systems and methodologies of groupingwage assignment information are inadequate.

Delivery of Wage Assignment Information. For a typical wage assignment,such as, for example, a child support obligation, an employer implementsthe wage assignment upon receipt of the wage assignment order. However,if the wage assignment order has been converted into an electronicformat, the wage assignment information must be transmitted to theemployer in a useable manner. Some employers are capable of receivingfiles electronically, but most employers are not equipped with thiscapability. Without these capabilities, an employer cannot receive wageassignment information electronically and automatically implementprocessing of the wage assignment. As such, the present systems andmethodologies are inefficient and undesirable. According to the presentsystems and methods, there is no means to deliver wage assignmentinformation to employers based on particular delivery requirements,where the information is initially collected from a state entity,translated into an electronic format, and then grouped for eachrecipient. Thus, the present systems and methodologies of deliveringwage assignment information are inadequate.

Electronic Implementation of Wage Assignment Information. For thereasons described above, systems and methods would be desirable thatcould collect wage assignment information, translate the wage assignmentinformation into an EDI file compatible with the X12 standard, group theinformation by recipient, and then deliver a single EDI file to the eachrespective recipient. For a typical wage assignment, such as, forexample, a child support obligation, such a system and method wouldallow for the collection of wage assignment orders for child supportpayments from state entities and, once collected, translate the wageassignment orders into an EDI file compatible with the X12 standard(e.g., the 521 record set), and then group the orders by recipient, andfinally deliver a single EDI file to each respective recipient forprocessing. However, as described above, the current systems andmethodologies reflect an unsatisfactory development of systems andmethods to collect, translate, group, and deliver wage assignmentinformation from an initiator of a wage assignment to a recipient. Ofcourse, once the recipient obtains the wage assignment, the processingand implementation of the payment and disbursement occur using any knownsystem or method.

For information on systems and methods for payment and disbursementprocessing generally, and for payment processing using debit-based EFTas well as for disbursement processing using addendum-based EDIspecifically, see U.S. patent application Ser. No. 08/941,187 of JohnPOLK, entitled “Method and Apparatus for Payment Processing UsingDebit-based Electronic Funds Transfer and Disbursement Processing UsingAddendum-based Electronic Data Interchange,” filed Sep. 30, 1997,incorporated herein by reference. U.S. patent application Ser. No.08/941,187 provides efficient apparatus and methods for processingpayments and disbursements, including wage assignments. However, U.S.patent application Ser. No. 08/941,187 does not provide a particularapparatus or method, whereby wage assignment information may becollected, translated, grouped, and delivered from an initiator to arecipient.

III. SUMMARY OF THE INVENTION

It is an object of an invention to provide a system for the collection,translation, grouping, and delivery of wage assignment information froman initiator to a recipient via an accumulator.

It is another object of an invention to provide a system for the receiptof wage assignment information at an initiator.

It is still another object of an invention to provide a system for thecollection of wage assignment information at an accumulator from aninitiator.

It is yet another object of an invention to provide a system whereby anaccumulator may translate wage assignment information into an electronicwage assignment format.

It is also an object of an invention to provide a system whereby anaccumulator may group electronic wage assignment information by batchingthe files for each respective recipient.

It is furthermore an object of an invention to provide a system wherebyan accumulator may deliver the batched wage assignment information filesto each respective recipient.

It is additionally an object of an invention to provide a system wherebya recipient may process wage assignments based on information receivedin a batched wage assignment information file.

To attain these and other objects, and in accordance with the purposesof the invention, as embodied and broadly described herein, one aspectof the invention includes a method consistent with the present inventionthat includes the steps, performed by a processor, of receiving a wageassignment at an initiator; dispatching the wage assignment from theinitiator to an accumulator; processing the wage assignment at theaccumulator; transmitting the wage assignment from the accumulator to arecipient; and implementing the wage assignment at the recipient.

In another aspect, the invention includes a method of processing a wageassignment at an initiator, comprising the steps, performed by aprocessor, of receiving a wage assignment; inputting the wage assignmentinto a database; and transmitting the wage assignment to an accumulator.

In yet another aspect, the invention includes a method of processingwage assignments at an accumulator, comprising the steps, performed by aprocessor, of collecting a plurality of wage assignments from aplurality of initiators; translating the wage assignments into fileswith a standard wage assignment format, the format including data in atleast one data field; grouping the standard wage assignment format filesinto batch files based on the data stored in at least one data field ofthe standard wage assignment format; and delivering a batch file to eachof a plurality of recipients.

In still another aspect, the invention includes a method of processing awage assignment at a recipient, comprising the steps, performed by aprocessor, of receiving a wage assignment from an accumulator;processing the wage assignment; and implementing the wage assignmentagainst a wage of an employee.

Additional aspects of the invention are disclosed and defined by theappended claims. It is to be understood that both the foregoing generaldescription and the following detailed description are exemplary andexplanatory and are intended to provide further explanation of theinvention as claimed.

IV. BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings are included to provide a furtherunderstanding of the invention, are incorporated in and constitute apart of this specification, illustrate preferred embodiments of theinvention, and, together with the description, serve to explain theprinciples of the invention.

In the drawings,

FIG. 1 is a block diagram of a wage assignment collection and deliverysystem;

FIG. 2A is a block diagram of an alternative wage assignment collectionand delivery system;

FIG. 2B is a block diagram of another alternative wage assignmentcollection and delivery system;

FIG. 3 is a flow diagram of a method for processing wage assignmentinformation in a wage assignment collection and delivery system, asshown in FIG. 1;

FIG. 4 is a block diagram of an initiator, as shown in FIG. 1;

FIG. 5 is a block diagram of an accumulator, as shown in FIG. 1;

FIG. 6 is a block diagram of the processing performed during collectionby an accumulator, as shown in FIG. 5;

FIG. 7 is a block diagram of the processing performed during translationby an accumulator, as shown in FIG. 5;

FIG. 8 is a block diagram of the processing performed during grouping byan accumulator, as shown in FIG. 5;

FIG. 9 is a block diagram of the processing performed during delivery byan accumulator, as shown in FIG. 5;

FIG. 10 is a block diagram of a recipient, as shown in FIG. 1;

FIG. 11 is a block diagram of a data processor at an initiator, as shownin FIG. 4;

FIG. 12 is a block diagram of a data processor at an accumulator, asshown in FIG. 5;

FIG. 13 is a block diagram of a data processor at a recipient, as shownin FIG. 10;

FIGS. 14A-14B depict a sample of an order/notice to withhold income forchild support, as may be used by a wage assignment collection anddelivery system, such as the system shown in FIG. 1;

FIGS. 15A-15B depict a sample of an order/notice to withhold income forchild support containing data for purposes of illustration, as may beused by a wage assignment collection and delivery system, such as thesystem shown in FIG. 1;

FIG. 16 is a sample of the contents of the wage assignment informationdatabase in the, data processor at the initiator shown in FIG. 11, usingthe illustrative data from FIGS. 15A-15B;

FIG. 17 is a sample of the contents of the wage assignment informationdatabase in the data processor at the accumulator shown in FIG. 2, usingthe illustrative data from FIGS. 5A-15B;

FIG. 18 is a sample of the contents of the wage assignment informationfile database in the data processor at the accumulator shown in FIG. 12,using the illustrative data from FIGS. 5A-15B as well as otherillustrative data;

FIGS. 19A-19B depict a sample of an order/notice to withhold income forchild support containing field identifiers for purposes of illustratingmapping rules; FIGS. 19C-19F are samples of mapping rules correspondingto FIGS. 19-A19B, such as mapping rules that would appear in the mappingrules database in the data processor at the accumulator shown in FIG.12;

FIG. 20 is a sample of the contents of the EDI wage assignmentinformation file database in the data processor at the accumulator shownin FIG. 12, using the illustrative data from FIGS. 15A-15B as well asother illustrative data;

FIG. 21 is a sample of the contents of the EDI batch file database inthe data processor at the accumulator shown in FIG. 12, using theillustrative data from FIGS. 15A-15B as well as other illustrative data;

FIG. 22 is a sample of the contents of the recipient delivery databasein the data processor at the accumulator shown in FIG. 12, containingdata corresponding to illustrative parameters for an exemplary recipientdelivery database;

FIG. 23 is a sample of the contents of a single EDI file from the EDIbatch file database corresponding to a single recipient from therecipient delivery database in the data processor at the accumulatorshown in FIG. 12, containing illustrative data for delivery to anillustrative recipient;

FIG. 24 is a sample of the contents of the EDI file database in the dataprocessor at the recipient shown in FIG. 13, containing illustrativedata for a single illustrative recipient;

FIG. 25 is a flow diagram of a method for processing wage assignmentinformation in a wage assignment collection and delivery system, inaccordance with one embodiment of the invention, as shown in FIG. 1;

FIG. 26 is a flow diagram of a method for processing wage assignmentinformation at an initiator, in accordance with one embodiment of theinvention, as shown in FIG. 25;

FIG. 27 is a flow diagram of a method for processing wage assignmentinformation at an accumulator, in accordance with one embodiment of theinvention, as shown in FIG. 25;

FIG. 28 is a flow diagram of a method for processing wage assignmentinformation at a recipient, in accordance with one embodiment of theinvention, as shown in FIG. 25;

FIG. 29 is a flow diagram of a method for processing wage assignmentinformation in a wage assignment collection and delivery system, inaccordance with an alternative embodiment of the invention, as shown inFIG. 2B;

FIG. 30 is a flow diagram of a method for processing wage assignmentinformation at an initiator, in accordance with an alternativeembodiment of the invention, as shown in FIG. 29;

FIG. 31 is a flow diagram of a method for processing wage assignmentinformation at an accumulator, in accordance with an alternativeembodiment of the invention, as shown in FIG. 29;

FIG. 32 is a flow diagram of a method for processing wage assignmentinformation at a recipient, in accordance with an alternative embodimentof the invention, as shown in FIG. 29.

V. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

A preferred embodiment of this invention, known as NEWWS™ (NationalEmployer Wage Withholding Service), is presently marketed by LockheedMartin IMS. The scope of the present invention, however, encompassesmodifications and variations as described by the methods and apparatusdescribed herein or as contained within the scope of, the listed claimsand their equivalents.

A. Introduction

The system of a preferred embodiment of the invention avoids theinefficiencies and shortcomings of the present wage assignment systemsand methodologies by providing for the electronic collection,translation, grouping, and delivery of wage assignment information.Systems consistent with the present invention include receiving wageassignment information at an initiator regarding a wage assignment. Theinitiator gathers the wage assignment information and transmits theinformation to an accumulator. The accumulator collects the wageassignment information and then translates the information into anelectronic format, such as an electronic file that corresponds to thepublic EDI standard established by the X12 standard. After translation,the accumulator then batches the electronic files based on a field inthe electronic format. The accumulator then delivers a single batch fileto each recipient. Upon receipt of a batch file, a recipient thenprocesses the wage assignment and implements a funds or asset transferin any known manner.

A preferred system consistent with the invention comprises severalcomponents, including a plurality of initiators, an accumulator, and aplurality of recipients. Each initiator receives and processes wageassignment information for various individuals. The initiators store andmaintain the wage assignment information in a database and periodicallytransmit the database to an accumulator. The accumulator serves as aprocessing station (also known as a Value Added Network, or VAN) betweenthe plurality of initiators and the plurality of recipients. Inparticular, the accumulator collects wage assignment information fromeach of the plurality of initiators and ensures that the informationfrom each initiator is valid. The accumulator then translates the wageassignment information into a standard format, for example, into an EDIfile, such as the 521 record set. The accumulator then batches the EDIfiles according to the recipient indicated in the EDI file and deliversa single EDI file to each of the plurality of recipients. The recipientprocesses and implements the wage assignment through any of severalknown methods. For an example of the implementation of a wageassignment, refer to U.S. patent application Ser. No. 08/941,187.

B. System

FIG. 1 shows a wage assignment collection and delivery system accordingto one embodiment of the present invention. System 100 includes aplurality of initiators 110 _(1-n), an accumulator 120, and a pluralityof recipients 130 _(1-m). Initiators 110 _(1-n) may represent any entitythat initiates a wage assignment. Accumulator 120 is the processingstation that receives wage assignments from initiator 110 _(1-n),processes the wage assignments, and then transmits the wage assignmentsto recipients 130 _(1-m). Recipients 130 _(1-m) entail those entitiesthat receive and implement wage assignments.

FIG. 2A shows a wage assignment collection and delivery system accordingto an alternative embodiment of the present invention. System 200includes a plurality of agencies 210 _(1-n), an accumulator 220, and aplurality of employers 230 _(1-m). In this embodiment, the plurality ofagencies 110 _(1-n) are agencies that may initiate a wage assignment,and the plurality of employers 230 _(1-m) are the employers that mayreceive and implement wage assignments. Similar to FIG. 1, accumulator120 in FIG. 2A is the processing station that receives wage assignmentsfrom agencies 210 _(1-n), processes the wage assignments, and thentransmits the wage assignments to employers 230 _(1-m).

FIG. 2B shows a wage assignment collection and delivery system accordingto another alternative embodiment of the present invention. System 205includes a plurality of states 215 _(1-n), an accumulator 220, and aplurality of employers 235 _(1-m). In this embodiment, the plurality ofstates 215 _(1-n) are states or state entities that may initiate a wageassignment, and the plurality of employers 235 _(1-m) are the employersthat may receive and implement wage assignments. Similar to FIG. 1 andFIG. 2A, accumulator 120 in FIG. 2B is the processing station thatreceives wage assignments from states 215 _(1-n), processes the wageassignments, and then transmits the wage assignments to employees 235_(1-m). In a preferred embodiment of the system shown in FIG. 2B, theplurality of states 215 _(1-n) are state agencies that initiate ChildSupport Orders requiring wage assignments for noncustodial parents, andthe plurality of employers 235 _(1-m) are the employers of thenoncustodial parents subject to the wage assignments pursuant to theChild Support Orders.

C. Process

FIG. 3 is a flow chart 300 illustrating the operation of a system 100 asshown in FIG. 1. As shown in FIG. 3, each initiator 110 inputs wageassignment information containing a wage assignment into a database thateach initiator maintains separately (step 310). After the wageassignment information is input into the database, each initiator 110transmits, such as, in a periodic batch of ASCII files, the wageassignment information stored in the database to accumulator 120 (step320). Accumulator 120 then collects all the wage assignment informationfrom all initiators ₁₁₀(step 325). Accumulator 120 next translates thewage assignment information into an electronic format, which preferablycomprises an EDI file using the 521 record set (step 330). Afteraccumulator 120 creates the EDI files, they are initially organizedbased on the initiator. After the translation, however, accumulator 120reorganizes the wage assignment files based on one of the data fields,such as, for example, element BPR10 of the 521 record set, whichindicates the company initiating the funds transfer (i.e., employer).During this grouping (or batching), a batch of EDI files are created,preferably so that each EDI file is batched based on the employer (step340). Accumulator 120 then delivers the batched EDI files to each of theplurality of recipients 130 (step 350). The delivery medium thataccumulator 120 uses to deliver the batched EDI files to each of theplurality of recipients 130 depends on the capability of each recipient.For example, accumulator 120 may transmit an EDI file electronically tothe most sophisticated recipients 130, while other recipients 130 mayaccess a web page bulletin board (not shown) that is maintained byaccumulator 120, while still other recipients 130 may receive the filesvia facsimile, and while still other recipients 130 may receive theirfiles by mail. Whatever the delivery means, once received, each of theplurality of recipients 130 then processes the wage assignment andinitiates a funds transfer through any known manner (step 360). Notably,a detailed description of the methods of operation of systems consistentwith the operation of this system are provided in FIGS. 25-32.

D. Components

FIG. 4 illustrates one representative embodiment of an initiator 110shown in FIG. 1. As shown in FIG. 4, initiator 110 includes inputstation 405, data processor 410, and transmission means 420. Inputstation 405 provides for the input of wage assignments into a databaseat initiator 110. Input station 405 may include either manual orelectronic means for inputting wage assignments into a wage assignmentinformation database. Input station 405 may also include an opticalcharacter reader (OCR). Data processor 410 contains the database createdby input station 405. Similarly, data processor 410 provides for theperiodic transmission of the contents of the wage assignment informationdatabase to accumulator 120 via transmission means 420. Although dataprocessor 410 preferably transmits the contents of the databaseelectronically, initiator 110 may also transmit the database by othermeans, including by manual means. Thus, transmission means 420 includesboth electronic and non-electronic means by transmission. A detaileddescription of data processor 410 is provided in FIG. 11.

FIG. 5 illustrates one representative embodiment of accumulator 120shown in FIG. 1. As shown in FIG. 5, accumulator 120 includes dataprocessor 505, collection processing 510, translation processing 520,grouping processing 530, and delivery processing 540. After initiator110 transmits a wage assignment to accumulator 120, data processor 505at accumulator 120 collects the wage assignment during collectionprocessing 510. Collection processing 510 includes the collection of aplurality of wage assignment information from a plurality of initiators110. Generally, the plurality of initiators 110 transmits a plurality ofwage assignment information to accumulator 120 in the form of ASCIIformat. Thereafter, translation processing 520 converts the wageassignment information into a standardized electronic format such as,for example, an EDI file using the X12 standard. Grouping processing 530then batches the EDI files based on one data field from the EDI file.Preferably, the data field on which the batching occurs is the datafield for the recipient. In this manner, grouping processing 530 batchesthe EDI files based on the recipient. Delivery processing 540 thendelivers a single EDI file to each of a plurality of recipients 130.Notably, although delivery processing preferably occurs by electronicmeans, delivery processing 540 may take place by electronic, manual, orother means. Nonetheless, as noted above, in a preferred implementation,the EDI files are batched based on recipient, and therefore, deliveryprocessing 540 dispatches a single EDI file from accumulator 120 to eachof a plurality of recipients 130. A detailed description of dataprocessor 505 is provided in FIG. 12.

FIG. 6 illustrates one representative embodiment of collectionprocessing 510 shown in FIG. 5. As shown in FIG. 6, collectionprocessing 510 includes a plurality of wage assignment information 610_(1-n) and wage assignment information file 620. Wage assignmentinformation 610 _(1-n), which are shown in FIG. 6 as wage assignmentinformation 610 ₁, wage assignment information 610 ₂, wage assignmentinformation 610 _(n), is representative of the plurality of wageassignments received from a plurality of initiators 110. As shown inFIG. 6, the plurality of wage assignment information 610 _(1-n), arecollected by accumulator 120 and placed in wage assignment informationfile 620. Generally, the plurality of wage assignment information 610_(1-n) are in the ASCII format. Wage assignment information file 620 issimply a database containing the plurality of wage assignmentinformation 610 _(1-n).

FIG. 7 illustrates one representative embodiment of translationprocessing 520 shown in FIG. 5. As shown in FIG. 7, translationprocessing 520 includes wage assignment information file 620, mapprocessing 710, mapping rules 715, and EDI wage assignment informationfile 720. In translation processing 520, as shown in FIG. 7, wageassignment information file 620 is subject to map processing 710. In mapprocessing 710, mapping rules 715 are applied to the contents of wageassignment information file 620. In a preferred implementation, mappingrules 715 contain the mapping rules for the 521 record set of the X12standard. Thus, in this preferred implementation, each wage assignmentinformation in wage assignment information file 620 is translated intoan EDI format pursuant to mapping rules 715 by map processing 710.Following map processing 710, each wage assignment information containedin wage assignment information file 620 has been translated into anelectronic file, preferably an EDI file. These EDI files are thenrecorded in EDI wage assignment information file 720.

FIG. 8 illustrates one representative embodiment of grouping processing530 shown in FIG. 5. As shown in FIG. 8, grouping processing 530includes a plurality of wage assignment information as EDI files,including wage assignment information as EDI file (for Recipient₁) 810,wage assignment information as EDI file (for Recipient₂) 815, wageassignment information as EDI file (for Recipient₁) 820, and wageassignment information as EDI file (for Recipient_(n)) 825. Groupingprocessing 530 also includes batch processing 830, and a plurality ofEDI batch files for recipients, including EDI batch file for Recipient₁840, EDI batch file for Recipient₂ 850, and EDI batch file forRecipient_(n) 860. FIG. 8 contains examples showing the operation ofbatch processing 830, which references both the plurality of wageassignment information as EDI files and the plurality of EDI batch filesfor recipients. These examples are based on references to Recipient₁ andRecipient₂ as well as Recipient_(n).

As shown in FIG. 8, wage assignment information as EDI file (forRecipient₁) 810 and wage assignment information as EDI file (forRecipient₁) 820 are two EDI files for Recipient'. Wage assignmentinformation as EDI file (for Recipient₂) 815 is a single EDI file forRecipient₂. Wage assignment information as EDI file (for Recipient_(n))825 shows that an unlimited number of other EDI files may be availablefor an unlimited number of other recipients. During grouping processing530, batch processing 830 batches the EDI files based on one data fieldfrom the EDI file. A described above, in a preferred implementation,batch processing 830 utilizes the recipient field from the EDI file(e.g., element BPR10 of the 521 record set) as the field for purposes ofbatch processing 830. FIG. 8 depicts batch processing based upon thispreferred implementation. Thus, as shown in FIG. 8, EDI batch file forRecipient, 840 shows wage assignment information as EDI file (forRecipient₁) 810 and wage assignment information as EDI file (forRecipient₁) 820 as batched in a single EDI batch file for Recipient₁.Similarly, EDI batch file for Recipient₂ 850 contains wage assignmentinformation as EDI file (for Recipient₂) 815 as a single batch file forRecipient₂. These examples for Recipient, and Recipient₂ would beimplemented similarly for a plurality of other Recipients, such as, forexample, Recipient_(n). Thus, as shown in EDI batch file forRecipient_(n) 860, wage assignment information as EDI file (forRecipient_(n)) 825 would be contained in a single batch file forRecipient_(n).

FIG. 9 illustrates one representative embodiment of delivery processing540 shown in FIG. 5. As shown in FIG. 9, delivery processing 540includes wage assignment EDI batch file for Recipient_(s) 910, delivery920, FTP 930, Internet 940, tape 950, diskette 960, and Recipient_(x)970. Delivery processing 540 takes an EDI batch file containing wageassignment information for Recipient_(x) 910 and implements delivery920. Delivery 920 entails the delivery of the EDI batch file to arecipient 130, i.e., Recipient, 970. Delivery 920 may take place by oneof several methods, such as, for example, FTP 930, Internet 940, a tape950, and diskette 960. Other delivery methods are also available (notshown). Whatever method utilized by delivery 920, the wage assignmentEDI batch file for Recipient_(x) 910 is delivered to Recipient_(x) 970.In a preferred implementation, delivery processing 540 contains adatabase indicating the preferred method of delivery for each of aplurality of recipients, such as, Recipient_(x) 970. A detaileddescription of the database indicating the preferred method of deliveryis provided in FIG. 22.

FIG. 10 illustrates one representative embodiment of recipient 130 shownin FIG. 1. As shown in FIG. 10, recipient 130 includes transmissionmeans 1005, data processor 1010, payroll department 1020, and wageassignment 1030. Recipient 130 receives wage assignment information fromaccumulator 120 via transmission means 1005. As described above, in apreferred implementation, transmission means 1005 receives an EDI filecontaining wage assignment information electronically. However,recipient 130 may also receive wage assignment information viatransmission means 1005 in other forms, such as, for example, diskette.Whatever the form, once recipient 130 receives the wage assignmentinformation, the wage assignment information is recorded in dataprocessor 1010. Recipient 130 then processes the wage assignment in dataprocessor 1010, which includes informing payroll department 1020 of thewage assignment. Note that payroll department 1020 may include anyimplementation of the wage assignment, manual or electronic. Payrolldepartment 1020 then implements wage assignment 1030. In implementingwage assignment 1030, payroll department offsets or withholds a portionof the salary of the employee subject to the wage assignment. Suchpayment and disbursement processing may occur by any known system ormethod. A detailed description of data processor 1010 is provided atFIG. 13.

FIG. 11 illustrates one representative embodiment of data processor 410shown in FIG. 4, in a wage assignment collection and delivery system asshown in FIG. 1. As shown in FIG. 11, data processor 410 at initiator110 preferably includes one or more data processors 1100 equipped withconventional hardware and having operating software to support a centralprocessing unit (“CPU”) 1110, a random access memory (“RAM”) 1120, amonitor 1130, an input/output (I/O) controller 1140, a data storagedevice (disk) 1150, an input device 1160, and an output device 1170.Although not depicted, processing station 300 is also capable ofsupporting peripheral equipment, such as, for example, scanners,printers, modems, etc., in conventional manners.

As shown in FIG. 11, CPU 1110 is directly coupled to each of RAM 1120,I/O controller 1140, and disk 1150. CPU 1110 operates by accessing RAM1120 and disk 1150 in any conventional manner to execute program code(not shown) stored in at least one of RAM 1120 and disk 1150 to carryout the functions and acts described in connection with the operation ofprocessing station 1100. CPU 1110 preferably comprises at least onehigh-speed digital data processor adequate to execute program modulesconsistent with the invention, such as the accumulation, processing,storage, and transmission of wage assignment information.

In one embodiment, processing station 1100 shown in FIG. 11 located atan initiator 110, such as, for example, a state child supportdepartment, operates to collect wage assignment information frompersons, such as, for example, persons subject to mandatory childsupport payments. In such an example, a case worker at a state childsupport department inputs data at input device 1160 regarding anoncustodial parent who is subject to a Child Support Order. Data inputat input device 1160 is received at CPU 1110 through I/O controller 1140and stored in wage assignment information database 1152, which is storedin disk 1150. Preferably, processing station 1100 periodically transmitsa batch of files through output device 1170 containing the wageassignment information stored in wage assignment information database1152 to accumulator 120 as shown in FIG. 1. Although it is preferable totransmit the database as a batch of files, processing station 1100 couldtransmit the wage assignment information to accumulator 120 using otherequivalent electronic means, such as E-mail, Internet bulletin boards,etc., or non-electronic means, such as Federal Express and the U.S.Postal Service. In the case of non-electronic means, processing station1100 would either transmit a printout of the database or download thedatabase onto a disk and transmit the disk to accumulator 120. Once thenon-electronic information arrived at accumulator 120, the wageassignment information would then need to be manually input into thedata processor at accumulator 120.

As shown in FIG. 11, disc 1150 preferably comprises a large capacitymemory capable of maintaining wage assignment information database 1152.Wage assignment information database 1152 contains data corresponding toa wage assignment, such as, for example, a Child Support Order. Wageassignment information database 1152 can be structured in many forms andtypically includes informational fields for the name of the originatingstate, the name of the originating jurisdiction, the date, and employeridentification (which is normally the employer's Federal TaxIdentification Number), the employer name, the employer address, thename of the custodial parent, the social security number of thenon-custodial parent, the name of a custodial parent, the orderedtermination date (which indicates when the child support is no longermandatory), the dollar amount, etc. Data contained in wage assignmentdatabase 1152 may be periodically obtained and updated from input device1160. Samples of the records and the respective fields contained in wageassignment information database 1152 is shown in and described inconnection with FIG. 16.

FIG. 12 illustrates one representative embodiment of data processor 505shown in FIG. 5, in a wage assignment collection and delivery system asshown in FIG. 1. As shown in FIG. 12, accumulator 120 preferablyincludes one or more processing stations 1200, which could be aconventional personal computer, mainframe, or equivalent, each equippedwith conventional hardware and having operating software to support acentral processing unit (“CPU”) 1210, a random access memory (“RAM”)1220, a monitor 1230, an input/output (I/O) controller 1240, a datastorage device (disk) 1250, an input device 1260, and an output device1270. Although not depicted, processing station 1200 is also capable ofsupporting peripheral equipment such as scanners, printers, modems,etc., in conventional manners.

As shown in FIG. 12, CPU 1210 is directly coupled to each of RAM 1220,I/O controller 1240, and disk 1250. CPU 1210 operates by accessing RAM1220 and disk 1250 in any conventional manner to execute program code(not shown) stored in at least one of RAM 1220 and disk 1250 to carryout the functions and acts described in connection with the operation ofprocessing station 1200. CPU 1210 preferably comprises at least onehigh-speed digital data processor adequate to execute program modulesconsistent with the invention, such as the accumulation, transmission,organization, processing, and storage operations as well as thecollection, translation, grouping, and delivery of wage assignmentinformation.

In one embodiment, processing station 1200 receives wage assignmentinformation at periodic intervals through input device 1260. In apreferred embodiment, processing station 1200 receives wage assignmentinformation at periodic intervals through input device 1260 in the formof electronic files containing the data relating to Child Support Ordersfrom a plurality of states 215, as shown in FIG. 2B. CPU 1210 thentemporally stores either the wage assignment information or the wageassignment information file in wage assignment information database 1252or in wage assignment information file database 1253, both of which arestored in disk 1250. If the wage assignment information is not formattedin a file, CPU 1210 initially stores the wage assignment information inwage assignment information database 1252 and then converts the wageassignment information into a wage assignment file and stores the filein wage assignment information file database 1253. However, if the wageassignment information is initially formatted in a file, then CPU 1210stores the wage assignment information directly in wage assignmentinformation file database 1253. Next, preferably, CPU 1210 translatesthe files in wage assignment information file 1253 into an EDIcompatible file according to the ANSI X12 standard, specifically in the521 record set, and these EDI files are then placed in EDI wageassignment file information file database 1254, which is stored in disk1250. In order to translate the files into an EDI file, CPU 1210accesses a rules database, such as a mapping rules database 1251, whichis stored in disk 1250. Mapping rules database 1251 contains the codesneeded by CPU 1210 to translate a file received from an initiator intoan electronic file, preferably into an EDI file corresponding to the 521record set. After translation, processing station 1200 then batches theEDI files in a database, such as EDI batch file database 1255, which isstored in disk 1250. In a preferred implementation, CPU 1210 batches theEDI files together based on a field containing information about theemployer of the noncustodial parent (for example, element BPR10 of the521 record set). In this implementation, CPU 1210 gathers all EDI filesthat indicate the same employer, regardless of the state of jurisdictionof origin, and batches those EDI files together in a single batched EDIfile. Thereafter, CPU 1210 delivers the batched EDI file through outputdevice 1270 to a recipient 130 on a periodic basis, which corresponds tothe indicated recipient among the plurality of recipients 130.

Notably, in the preferred embodiment discussed above, while it ispreferable to send a batched EDI file to an indicated employer, theindicated employer may not be capable of electronically receiving EDIfiles for processing. To account for this possibility, processingstation 1200 has a recipient delivery database 1257, which is stored indisk 1250. Prior to transmitting a batched EDI file to an indicatedemployer, CPU 1210 accesses recipient rules database 1257. If recipientrules database 1257 indicates that the indicated employer can receiveEDI file, then the EDI file is transmitted to the indicated employerelectronically. Otherwise, CPU 1210 transmits the EDI file (i.e.,preferably containing a batch file of one or more EDI files using the521 record set) to the indicated employer through output device 470 byany transmission medium. In other words, the EDI file may even be sentthrough E-mail, facsimile transmission, or even the mail. As a furtheralternative to transmitting the files to the employer, CPU 1210 couldtransmit the EDI file via output device 1270 to a Web page or bulletinboard (not shown). The indicated employer would receive the EDI file byaccessing the Web page or bulletin board and then downloading thebatched files. These alternative methods would use any conventionalInternet server or computer system, access protocols, uploadingprotocols, downloading protocols, and security protocols. Data containedin one or more of these databases 1251, 1252, 1253, 1254, 1255, and 1257may be periodically obtained and updated from input device 1260. Samplesof the records and the respective fields contained in databases 1251,1252, 1253, 1254, 1255, and 1257 are shown in and described inconnection with FIGS. 17-23.

FIG. 13 illustrates one representative embodiment of data processor 1010shown in FIG. 10, in a wage assignment collection and delivery system asshown in FIG. 1. As shown in FIG. 13, each recipient 130 preferablyincludes one or more processing stations 1300, which could be aconventional personal computer, mainframe, or equivalent, each equippedwith conventional hardware and having operating software to support acentral processing unit (“CPU”) 1310, a random access memory (“RAM”)1320, a monitor 1330, an input/output (I/O) controller 1340, a datastorage device (disk) 1350, an input device 1360, and an output device1370. Although not depicted, processing station 1300 is capable ofsupporting peripheral equipment such as scanners, printers, modems,etc., in conventional manners.

As shown in FIG. 13, CPU 1310 is directly coupled to each of RAM 1320,I/O controller 1340, and disk 1350. CPU 1310 operates by accessing RAM1320 and disk 1350 in any conventional manner to execute program code(not shown) stored in at least one of RAM 1320 and disk 1350 to carryout the functions and acts described in connection with the operation ofprocessing station 1300. CPU 1310 preferably comprises at least onehigh-speed digital data processor adequate to execute program modulesconsistent with the invention, such as the accumulation, storage, andprocessing of wage assignment information and the implementation of wageassignments.

In a preferred embodiment, processor station 1300 receives wageassignment information transmitted from accumulator 120 through anelectronic medium by inputting an EDI file directly into CPU 1310through input device 1360. Data input at input device 1360 is receivedat CPU 1310 through I/O controller 1340 and stored in EDI file database1352, which is stored in disk 1350. Other embodiments, however, includedownloading the wage assignment information from an Internet bulletinboard, from E-mail, or inputting the wage assignment informationmanually. Whatever the means of transmission of wage assignmentinformation, in a preferred implementation, recipient 130 is theemployer of the noncustodial parent subject to a wage assignment, andthat assignment is then implemented in a manner as described in U.S.patent application Ser. No. 08/941,187. Recipient 130, however, canprocess the wage assignment in any manner currently known in the art.Regardless of the manner of implementation, the data contained indatabase 1352 may be periodically obtained and updated from input device1360. Samples of the records and the respective fields contained indatabase 1352 is shown in and described in connection with FIG. 24.

E. Database Formats

In FIGS. 11-13, a number of databases are referenced with respect to thewage assignment collection and delivery systems shown in FIG. 1 and FIG.2B. The following paragraphs describe these databases, but for purposesof illustration, these databases are depicted containing sample data. Infact, the samples of the contents of wage assignment informationdatabase 1152, mapping rules database 1251, wage assignment informationdatabase 1252, wage assignment information file database 1253, EDI wageassignment information file database 1254, EDI batch file database 1255,recipient delivery database 1257, and EDI file database 1352 are shownin FIGS. 16-24. The specific data and fields illustrated in thesefigures represent only one possible embodiment of a type of record thatcan be stored in the databases. For purposes of illustration, the recorddepicted is that of the preferred embodiment, i.e., the 521 record setof the X12 standard. Therefore, in most cases, the fields shown in FIGS.16-24 are relatively straight-forward and self-explanatory. However,note that, in addition to the disclosed databases, the data and fieldsof these databases, as well as the number of databases, can be readilymodified from the described embodiments, for example, to include more orfewer data fields or different or additional records.

FIG. 14A-14B depict a sample of an order/notice to withhold income forchild support, i.e., a Child Support Order. As shown in FIG. 14A-14B,the Child Support Order contains a plethora of information relating to awage assignment for purposes of a child support obligation. Nonetheless,the form depicted in FIGS. 14A-14B is a standard Child Support Order, asused by judicial entities and implemented by state agencies. For thatreason, the form depicted in FIGS. 14A-14B is hereby incorporated byreference as well as reproduced for purposes of reference in FIGS.14A-14B. For the following descriptions, FIGS. 14A-14B are used as areference for purposes of providing a working example of the databasesin the wage assignment collection and delivery systems shown in FIG. 1and FIG. 2B.

FIGS. 15A-15B depict a sample of a Child Support Order containing sampledata for purposes of illustration. This sample data will be used as thesample content for the databases described in FIGS. 16-24. As shown inFIGS. 15A-15B, the sample Child Support Order has been issued in theState of Virginia by a court in Alexandria, with a order date of Jun.12, 1998 and a court number of 98-123. The sample order is directed tothe employer of John J. Doe which is Y Corp., located at 123 MainStreet, Anytown, Va. 12345-00000. As shown in the Child Support Order,the social security number of John Doe is 123-45-6789, the caseidentifier is 98-123, and the custodial parent is Jane Doe. Furthermore,as also shown in this sample Child Support Order, the child's name isSusie Doe, who has a date of birth of Jun. 1, 1990. As stated in thesample order, the Child Support Order pertains to an employer in theState of Virginia, and the order requires a wage assignment against thewages of John Doe at Y Corp. until Jun. 1, 2008. Under the terms of thesample Child Support Order, $800.00 a month is required in childsupport, and $100.00 a month is required in medical support; thus atotal of $900.00 a month is required for the wage assignment. Theforegoing information from the sample Child Support Order is used forpurposes of illustration in FIGS. 16-24.

FIG. 16 illustrates a sample of the contents of wage assignmentinformation database 1152 in data processor 410 at initiator 110 asshown in FIG. 11, using sample information in a preferred implementationof a wage assignment collection and delivery system. Wage assignmentinformation database 1152, contains a listing of the informationrelating to a wage assignment, such as the information contained in aChild Support Order, such as, for example, sample order 1500, asdepicted in FIGS. 15A-15B. As shown in FIG. 16, wage assignmentinformation database 1152 contains 8 numbered fields but provides for anunlimited number of additional fields. As also shown in FIG. 16, a wageassignment may contain various types of information, which are recordedin wage assignment information database 1152. The wage assignmentinformation in wage assignment information database 1152 may be recordedin any order.

FIG. 17 illustrates a sample of the contents of wage assignmentinformation database 1252 in data processor 505 at accumulator 120 asshown in FIG. 12, using sample information in a preferred implementationof a wage assignment collection and delivery system. Wage assignmentinformation database 1252 contains the same information as wageassignment information database 1152. Essentially, initiator 110transmits the contents of wage assignment information database 1152 toaccumulator 120. Following such transmission, accumulator 120 initiallyrecords the information received from initiator 110 in wage assignmentinformation database 1252. Wage assignment information database 1252 isthus a temporary database at accumulator 120.

FIG. 18 illustrates a sample of the contents of wage assignmentinformation file database 1253 in data processor 505 at accumulator 120as shown in FIG. 12, using sample information in a preferredimplementation of a wage assignment collection and delivery system. Asshown in FIG. 18, wage assignment information file database 1253contains nine fields but allows for an unlimited number of additionalfields. In one implementation, field 1 identifies initiator 110. Thus,as shown in FIG. 18, field 1 shows two initiators, labeled I₁ and I₂.For I₁, there is one file in wage assignment information file database1253, and for I₂ there are two files in wage assignment information filedatabase 1253. Significantly, as shown in FIG. 18, the order of theinformation in each field need not be standardized for purposes of wageassignment information file database 1253.

FIGS. 19A-19F illustrate a sample of the form and contents of mappingrules database 1251 in data processor 505 at accumulator 120 as shown inFIG. 12, using a sample mapping form and sample mapping rules for apreferred implementation of a wage assignment collection and deliverysystem. FIGS. 19A-19B demonstrate how a mapping database may be createdfor purposes of map processing. FIGS. 19A-19B depict the same ChildSupport Order of FIGS. 14A-14B, except that each entry possibility has amapping field. FIGS. 19A-19B show these mapping fields as fields 1 a-36d. Correspondingly, FIGS. 19C-19F depict a table containing the mappingfields of the Child Support Order shown in FIGS. 19A-19B. In a preferredimplementation, as depicted in FIGS. 19C-19F, the mapping fieldscorrespond to the 521 record set. Thus, in this preferredimplementation, the fields of the 521 record set correspond to thefields of mapping rules database 1251. Thus, when the wage assignmentcollection and delivery system translates a wage assignment to an EDIfile format, as in the above-described preferred embodiment, mappingrules database 1251 contains records having fields corresponding to, forexample, the fields identified in FIGS. 19C-19F.

FIG. 20 illustrates a sample of the contents of EDI wage assignmentinformation file database 1254 in data processor 505 at accumulator 120as shown in FIG. 12, using sample information in a wage assignmentcollection and delivery system. In a preferred implementation, usingmapping rules database 1251, data processor 505 at accumulator 120 mapsthe information contained in wage assignment information file database1253 to an EDI format, according to the fields set forth in mappingrules database 1251. In this manner, the information in wage assignmentinformation file database 1253 is placed in fields corresponding to themapping rules of mapping rules database 1251. As noted above, in apreferred implementation, mapping rules database 1251 contains themapping rules for the 521 record set. Once this mapping occurs, thefiles are placed in EDI wage assignment information file database 1254,as shown in FIG. 20. Thus, in this preferred implementation, usingmapping rules database 1251, each wage assignment is mapped to theproper field for the 521 record set. As shown in FIG. 20, fields 1 a-36d contain these fields of the 521 record set, which correspond to thetable shown in FIGS. 19C-19F. Thus, as shown in FIGS. 19C-19F and FIG.20, and using the mapping rules from mapping rules database 1251, field1 a corresponds to the name of the state, field 1 b corresponds to thename of the jurisdiction, field 2 corresponds to the date of the order,field 3 corresponds to the identifying number of the court, field 6 acorresponds to the withholder's name, field 36 d corresponds to thefacsimile number for the person named in field 36 a, etc. In FIG. 20,these fields are delineated as rows. In FIG. 20, the columns pertain tothe plurality of initiators 110, labeled I₁, I₂, I₃, etc.

FIG. 21 illustrates a sample of the contents of EDI batch file database1255 in data processor 505 at accumulator 120 as shown in FIG. 12, usingsample information in a wage assignment collection and delivery system.As shown in FIG. 21, in a preferred implementation, EDI batch filedatabase 1255 contains records having fields with identifierscorresponding to, for example, fields corresponding to the 521 recordset. Thus, EDI batch file database 1255 is similar to EDI wageassignment information file database 1254. However, EDI batch filedatabase 1255 contains EDI files that are batched by a particular field,such as, for example, one field from the 521 record set. In a preferredimplementation, EDI batch file database 1255 contains EDI files that arebatched on the recipient field (i.e., field BPR10 of the 521 recordset). Thus, in this preferred implementation, as shown in FIG. 21, EDIbatch file database 1255 contains EDI files, which are batched on therecipient.

FIG. 22 illustrates a sample of the contents of recipient deliverydatabase 1257 in data processor 505 at accumulator 120 as shown in FIG.12, containing sample information for a wage assignment collection anddelivery system. As shown in FIG. 22, a plurality of recipients 130 mayaccept the transmittal of EDI files by a number of methods, including,but not limited to, FTP, Internet, tape, and diskette. In a preferredimplementation, recipient delivery database 1257 contains the methods ofdelivery for EDI files from an accumulator 120 to a plurality ofrecipients 130. As shown in FIG. 22, for example, X Corp. accepts thetransmittal of EDI files via FTP and diskette but not via Internet ortape. Similarly, Y Corp. accepts the transmittal of EDI files via tapebut not via FTP, Internet, or diskette. Once accumulator 120 hasdetermined the proper means of transmittal, the batched EDI file for aparticular recipient 130 is removed from EDI batch file database 1255and transmitted in the manner indicated by recipient delivery database1257. Notably, as shown in FIG. 22, an unlimited number of deliverymethods are possible.

FIG. 23 does not depict any database but does illustrate a sample of anEDI file transmittal from data processor 505 at accumulator 120 as shownin FIG. 12, using sample information in a preferred implementation of awage assignment collection and delivery system. As shown in FIG. 23, EDIbatch file database 1255 contained two EDI files for one particularrecipient 130 (i.e., Y Corp.) from a plurality of recipients 130. Asshown in this example, recipient 130 is Y Corp., and EDI batch filedatabase 1255 contained two EDI files for Y Corp. within the EDI batchfile. Thus, when accumulator 120 delivers the EDI batch file to thisrecipient, the transmittal of the EDI batch file will include two EDIfiles. Notably, because this recipient accepts EDI files via FDP ordiskette, as indicated in the recipient delivery database 1257 as shownin FIG. 22, the transmittal of the EDI batch file shown in FIG. 23 maytake place by either of these two methods.

FIG. 24 illustrates a sample of the contents of EDI file database 1352from data processor 1010 at recipient 130 as shown in FIG. 13, using thesample information for a preferred implementation of a wage assignmentcollection and delivery system. As shown in FIG. 24, the contents of EDIfile database 1352 is the same as that transmitted from accumulator 120,as shown by the EDI batch file described in FIG. 23. Notably, however,depending on the method of delivery to recipient 110, EDI file database1352 may accept the information from accumulator 120 by any knowndelivery method, as indicated by recipient delivery database 1257 shownin FIG. 22.

F. Methods of Operation

As shown in FIG. 3, in processing a wage assignment from initiator 110to recipient 130 via accumulator 120, the system shown and described inconnection with FIG. 1 entails several distinct methods of operation.These methods include the processes that take place at initiator 110,the processes that take place at accumulator 120, and the processes thattake place at recipient 130. The steps associated with these processesare described in connection with FIGS. 25-32 and can be performed in anyorder, unless otherwise specified or dictated by the steps themselves.

In describing the processes consistent with the possible implementationsof a system as shown and described in connection with FIGS. 1 and 2B,alternative implementations of systems consistent with the invention atedescribed herein. For example, FIG. 25 illustrates the processesperformed by one embodiment of a wage assignment collection and deliverysystem as shown in FIG. 1. In this embodiment, initiator 110 initiates awage assignment (step 2510). Next, accumulator 120 collects, translates,groups, and delivers the wage assignment information (step 2520).Finally, recipient 130 receives a wage assignment for processing andimplementation (2530). FIGS. 26-28 depict flow diagrams illustrating theseries of particular steps performed by a wage assignment collection anddelivery system as shown in FIG. 25.

FIG. 26 illustrates the steps performed by initiator 110 in oneembodiment of a wage assignment collection and delivery system as shownin FIG. 1. As shown in FIG. 26, initiator 110 receives a wage assignmentorder for processing (step 2610). Next, initiator 110 inputs the wageassignment information into a database (step 2620). At some point intime, and preferably on a periodic basis, initiator 110 then transmitsthe wage assignment information contained in the wage assignmentinformation database to accumulator 120 (step 2630).

FIG. 27 illustrates the steps performed by accumulator 120 in oneembodiment of a wage assignment collection and delivery system as shownin FIG. 1. As shown in FIG. 27, accumulator 120 receives wage assignmentinformation from initiator 110 (step 2710). As described above,accumulator 120 may receive an unlimited number of wage assignmentinformation transmissions from an unlimited number of initiators 110.Accordingly, accumulator 120 collects all wage assignment informationinto a wage assignment information file (step 2720). After collection,in a preferred implementation, accumulator 120 then translates each wageassignment in the wage assignment information file into an EDI wageassignment information file (step 2730). After translation, accumulator120 then groups the EDI wage assignment information files by batchingthe files based on one field from the file. Preferably, the grouping ofEDI wage assignment information files during the batching process occurspursuant to the recipient field, so that the EDI batch files are batchedbased on the recipient (step 2740). After grouping, accumulator 120 thendelivers an EDI batch file to each of a plurality of recipients 130. Ina preferred implementation, where the EDI batch files are batched on therecipient, each recipient receives a single batch file containing allwage assignments for that recipient (step 2750).

FIG. 28 illustrates the steps performed by recipient 130 in oneembodiment of a wage assignment collection and delivery system as shownin FIG. 1. As shown in FIG. 28, recipient 130 receives an EDI batch filefrom accumulator agency 120 (step 2810). Next, recipient 130 processesthe wage assignment information from the EDI batch file (step 2820). Asnoted above, an EDI batch file may contain one or more EDI files.Finally, in processing the wage assignment information from the EDIbatch file, each wage assignment is implemented at recipient 130 byaccounts payable, human resources, or any other payroll system or method(step 2830). For example, in a preferred implementation relating to achild support obligation, a child support payment is withheld from thesalary of a noncustodial parent, and the payment is then disbursed tothe appropriate payee.

Similar to FIG. 25, FIG. 29 illustrates the processes performed byanother embodiment of a wage assignment collection and delivery systemas shown in FIG. 2B. In this embodiment, state 215 initiates a wageassignment (step 2910). Next, accumulator 120 collects, translates,groups, and delivers the wage assignment information (step 2920).Finally, employer 235 receives a wage assignment for processing (2930).FIGS. 30-32 depict flow diagrams illustrating the series of particularsteps performed by a wage assignment collection and delivery system asshown in FIG. 29.

FIG. 30 illustrates the steps performed by state 215 in one embodimentof a wage assignment collection and delivery system as shown in FIG. 2B.As shown in FIG. 30, state 215 receives a wage assignment order forprocessing (step 3010). Next, state 215 inputs the wage assignmentinformation into a database (step 3020). At some point in time, andpreferably on a periodic basis, state 215 then transmits the wageassignment information contained in the wage assignment informationdatabase to accumulator 120 (step 3030). Notably, FIG. 30 performs thesame steps as described in FIG. 26, except that instead of generallyreferencing an initiator 110 as in FIG. 26, FIG. 30 references a state215, which refers more specifically to a state or a state entity.

FIG. 31 illustrates the steps performed by accumulator 120 in oneembodiment of a wage assignment collection and delivery system as shownin FIG. 2B. As shown in FIG. 31, accumulator 120 receives wageassignment information from state 215 (step 3110). As described above,accumulator 120 may receive an unlimited number of wage assignmentinformation transmissions from an unlimited number of states 215. Next,accumulator 120 certifies the employer denoted by the wage assignmentinformation (step 3105). If the employer participates with theaccumulator (e.g., subscribes to the accumulator service), then the wageassignment information is accepted, but if the employer does notparticipate with the accumulator (e.g., does not subscribe to theaccumulator service), then the wage assignment information is rejected(step 3120). Accordingly, if the wage assignment information isaccepted, accumulator 120 collects all wage assignment information intoa wage assignment information file (step 3130). After collection, in apreferred implementation, accumulator 120 then translates each wageassignment in the wage assignment information file into an EDI wageassignment information file (step 3140). After translation, accumulator120 then groups the EDI wage assignment information files by batchingthe files based on one field from the file. Preferably, the grouping ofEDI wage assignment information files during the batching process occurspursuant to the recipient field, so that the EDI batch files are batchedbased on the recipient (step 3150). After grouping, accumulator 120 thendelivers an EDI batch file to each of a plurality of employers 235. In apreferred implementation, where the EDI batch files are batched on theemployer, each employer receives a single batch file containing all wageassignments for that employer (step 3160). Notably, FIG. 31 essentiallyperforms the same steps as described in FIG. 27, except that FIG. 31also contains an employer certification component.

FIG. 32 illustrates the steps performed by employer 235 in oneembodiment of a wage assignment collection and delivery system as shownin FIG. 2B. As shown in FIG. 32, employer 235 receives an EDI batch filefrom accumulator agency 120 (step 3210). Next, employer 235 processesthe wage assignment information from the EDI batch file (step 3220). Asnoted earlier, an EDI batch file may contain one or more EDI files.Finally, in processing the wage assignment information from the EDIbatch file, each wage assignment is implemented at employer 235 byaccounts payable, human resources, or any other payroll system or method(step 3230). Notably, FIG. 32 performs the same steps as described inFIG. 28, except that instead of generally referencing a recipient 130 asin FIG. 28, FIG. 32 more specifically references an employer 235.

VI. CONCLUSION

The systems consistent with the invention provide for more efficient andmore economical apparatus and methods for collection, translation,grouping, and delivery of wage assignment information. The systems firstcollect information relating to wage assignment information, translatethe information into an EDI format, which is commonly referred to as arecord set. Then, the EDI files are grouped based on the data containedin one or more element fields of the EDI record set and subsequentlydelivered to recipients who process the wage assignment information inany known method. This improved wage assignment collection and deliveryapparatus and methodology provide many advantages over the current wageassignment and collection and delivery technologies.

As described above, it will be apparent to those skilled in the art thatvarious modifications and variations can be made in the apparatus andmethods of the present invention without departing from the spirit andscope of the invention. Thus, it is intended that the present inventioncover the modifications and variations of this invention, provided theycome within the scope of the appended claims and their equivalents. Inthis context, equivalents means each and every implementation forcarrying out the functions recited in the claims, even if not explicitlydescribed herein.

1. A method of processing wage assignment information performed by adata processor, comprising: receiving wage assignment information from aplurality of sources; generating a mapping rules database, the mappingrules database including codes necessary to translate wage assignmentinformation into an electronic data interchange (EDI) compatible fileaccording to the ANSI X12 standard 521 record set; translating the wageassignment information into at least one EDI compatible electronic fileaccording to the ANSI X12 standard 521 record set using the mappingrules database.
 2. The method of claim 1 wherein the wage assignmentinformation is translated into more than one. EDI compatible electronicfile.
 3. The method of claim 2 including grouping the EDI compatibleelectronic files based on a field of the 521 record set.
 4. The methodof claim 3 wherein the EDI compatible electronic files are grouped basedon the BPR10 field of the 521 record set.
 5. The method of claim 3wherein the EDI compatible electronic files are grouped by the sameemployer.
 6. The method of claim 3 including generating a recipientdelivery database, and transmitting grouped EDI compatible electronicfiles to recipients based on recipient information stored in recipientdelivery database.
 7. The method of claim 1 wherein the translationincludes mapping the wage assignment information according to mappingfields in the mapping rules database, wherein the mapping fieldscorrespond to fields of the 521 record set.
 8. The method of claim 7wherein the mapping fields include at least the name of the state, thename of the jurisdiction, the date of the order, the identifying numberof the court, and the withholder's name.
 9. A tangible computer usablestorage medium having computer readable code embodied therein forprocessing wage assignment information, the computer readable codecomprising: a receiving module configured to receive wage assignmentinformation from a plurality of sources; a mapping rules database moduleconfigured to generate a mapping rules database, the mapping rulesdatabase including codes necessary to translate wage assignmentinformation into an electronic data interchange (EDI) compatible fileaccording to the ANSI X12 standard 521 record set; and a translationmodule configured to translate the wage assignment information into atleast one EDI compatible electronic file according to the ANSI X12standard 521 record set using the mapping rules database.
 10. Thetangible computer usable storage medium of claim 9 wherein thetranslation module is configured to translate wage assignmentinformation into more than one EDI compatible electronic file.
 11. Thetangible computer usable storage medium of claim 10 including a groupingmodule configured to group the EDI compatible electronic files based ona field of the 521 record set.
 12. The tangible computer usable storagemedium of claim 11 wherein the grouping module is configured to groupthe EDI compatible electronic files based on the BPR10 field of the 521record set.
 13. The tangible computer usable storage medium of claim 11wherein the grouping module is configured to group the EDI compatibleelectronic files by the same employer.
 14. The tangible computer usablestorage medium of claim 11 including, a recipient delivery databasemodule configured to generate a recipient delivery database, and atransmission module configured to transmit grouped EDI compatibleelectronic files to recipients based on recipient information stored inrecipient delivery database.
 15. The tangible computer usable storagemedium of claim 9 wherein the translation module is configured to mapthe wage assignment information according to mapping fields in themapping rules database, wherein the mapping fields correspond to fieldsof the 521 record set.
 16. The tangible computer usable storage mediumof claim 15 wherein the mapping fields include at least the name of thestate, the name of the jurisdiction, the date of the order, theidentifying number of the court, and the withholder's name.
 17. A dataprocessor comprising: a central processing unit; a receiving componentconfigured to receive wage assignment information from a plurality ofsources; a mapping rules database component configured to generate amapping rules database, the mapping rules database including codesnecessary to translate wage assignment information into an electronicdata interchange (EDI) compatible file according to the ANSI X12standard 521 record set; and a translation component configured totranslate the wage assignment information into at least one EDIcompatible electronic file according to the ANSI X12 standard 521 recordset using the mapping rules database.
 18. The data processor of claim 17wherein the translation component is configured to translate wageassignment information into more than one EDI compatible electronicfile.
 19. The data processor of claim 18 including a grouping componentconfigured to group the EDI compatible electronic files based on a fieldof the 521 record set.
 20. The data processor of claim 19 wherein thegrouping component is configured to group the EDI compatible electronicfiles based on the BPR10 field of the 521 record set.
 21. The dataprocessor of claim 19 wherein the grouping component is configured togroup the EDI compatible electronic files by the same employer.
 22. Thedata processor of claim 19 including, a recipient delivery databasecomponent configured to generate a recipient delivery database, and atransmission component configured to transmit grouped EDI compatibleelectronic files to recipients based on recipient information stored inrecipient delivery database.
 23. The data processor of claim 17 whereinthe translation component is configured to map the wage assignmentinformation according to mapping fields in the mapping rules database,wherein the mapping fields correspond to fields of the 521 record set.24. The data processor of claim 23 wherein the mapping fields include atleast the name of the state, the name of the jurisdiction, the date ofthe order, the identifying number of the court, and the withholder'sname.